System and methods for network control of 5G operation mode

ABSTRACT

Systems and methods provide for network-based selection of a UE device&#39;s 5G operation mode. A network device in a wireless core network receives a policy query for a user equipment (UE) device. The UE device is capable of 5G non-standalone (NSA) and 5G standalone (SA) operation modes. The network device identifies one or more of subscription data for the UE device, stored network data associated with the UE device, or dynamic network data relevant to the UE device. The network device assigns, based on the identifying, a radio access technology/frequency selection and prioritization (RFSP) value for the UE device. The network device sends the RFSP value to an access management function in the wireless core network for controlling selection of the 5G NSA operation mode or 5G SA operation mode.

BACKGROUND INFORMATION

The design and deployment of radio access networks (RAN) and corenetworks present certain challenges from a network-side perspective andan end device perspective. Fifth Generation (5G) networks, for example,may use different frequencies, different radio access technologies(RATs), and different core network functions that can provide animproved experience over current or legacy wireless networks (e.g.,Fourth Generation (4G) networks). However, the transition from suchsystems to 5G networks may require network service providers toconcurrently support users of older technologies and users of the newsystems within the limits of the available wireless spectrum. This canpresent challenges to the service providers, as some configurations atboth the network-side and end device-side may reduce the effective useof network resources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary multi-RAT environment inwhich systems and methods described herein may be implemented;

FIG. 2 is a diagram illustrating exemplary network elements forselection of a 5G operation mode in the multi-RAT environment of FIG. 1;

FIGS. 3A-3D are diagrams illustrating exemplary communications fornetwork selection of a 5G operation mode;

FIGS. 4A-4C are diagrams illustrating an exemplary embodiment of 5Goperation mode selection data;

FIG. 5 is a diagram illustrating exemplary components of a device thatmay correspond to one or more of the devices illustrated and describedherein;

FIG. 6 is a diagram illustrating a use case for network selection of a5G operation mode; and

FIG. 7 is a diagram illustrating a process for performing networkselection of a 5G operation mode.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings identify the same orsimilar elements. Also, the following detailed description does notlimit the invention.

A Fifth Generation (5G) new radio (NR) network may provide standalone(SA) and non-standalone (NSA) configurations. For an NSA configuration,a Long Term Evolution (LTE) Evolved Packet Core (EPC) may be usedtogether with other components of a 5G network; and for a SAconfiguration, a Next Generation Core (NGC) network may be used (NGC mayalso be referred to as a 5th Generation Core (5GC)). For NSA service, anLTE sub-6 cell (e.g., frequencies below 6 Gigahertz (GHz)) may be ananchor cell (e.g., Master Cell Group (MCG)) that provides all controlsignaling, and a NR band (e.g., using higher frequencies, such asmillimeter wave (mmWave) frequencies) may be used for a secondary cell(e.g., Secondary Cell Group (SCG)) that provides (different oradditional) data service. For SA service, a NR band may provide allcontrol signaling and data service.

Initial 5G deployments will utilize the NSA operation mode (which mayinclude “Option 3X” as defined by standardizing bodies). In Option 3X,the 5G NR RAN connects to the Evolved Packet Core. Over time, operatorswill move towards the SA architecture (also referred to as “Option 2” asdefined by standardizing bodies). The move to SA enables fullrealization of many of the features promised by 5G network technology,such as network slicing, increased security, ultra-reliable low latencycommunication (URLLC), industrial automation use cases, private networkenhancements, etc.

For a user equipment (UE) device to acquire wireless service of anetwork, the UE device has to first establish a wireless connection(e.g., a Radio Resource Control (RRC) connection) with a radio accessnetwork (RAN), and may authenticate, register, and establish a bearerwith a core network. UE devices may be configured to support one or moreoperation modes for 5G networks, such as SA and/or NSA. UE devices mayalso be configured to priority scan SA mode and, if the mode is found,attach to 5G network on the SA mode. Currently, UE devices are expectedto signal their capabilities (e.g. features supported, frequency bandssupported, operation modes supported, etc.) to the provider networkduring the initial attach procedure.

Current network standards do not provide guidance as to which operationmode (SA or NSA) should be supported and/or attached first when both arepossible in a given network (or portion of a network) for a particularUE device. Based on the signaled capabilities and/or configured prioritymode (e.g., SA mode over NSA) of a UE device, the network would simplyallow the UE device to connect in the highest operation mode (e.g., SAmode), assuming a frequency band supporting SA mode is available at thecurrent UE device location.

Radio frequency bands that support 5G networks may vary. However, forexample, a 5G network may include certain categories of radio frequencybands, such as those above 6 GHz and below 6 GHz, as well as othernomenclatures, such as sub-3 (e.g., below 3 GHz), mid-band (e.g.,between 3 GHz and 6 GHz), low band, mmWave, and so forth. Regardless ofthe nomenclatures or categories, using higher frequency bands typicallyincurs larger propagation loss. In addition, uplink (UL) and downlink(DL) coverage areas at mid-band frequencies may be significantlydifferent. For example, UL coverage may be smaller than DL coverage dueto transmit power and receiver capability differences (e.g., antennaarray, noise figure, etc.) between a UE device and a RAN device (e.g.,evolved Node B (eNB), next generation Node B (gNB), etc.).

As service providers plan 5G deployments, Sub-6 and mmWave bands mayinitially be used for NSA. As 5G networks are being deployed, mmWavebands and a few selected low bands may be enabled to support SA mode. As5G networks continue to expand in the future, mid-band (also referred toas C-band) may be deployed in SA mode.

Moreover, in the future, there may be a need for different networkbehaviors for different types of UE device using low bands. For example,IoT devices or telematics devices may require SA mode support in lowbands (e.g., to enjoy low latency services and ubiquitous coverage). Asanother example, a service provider may prefer to have dual NSA- andSA-capable smartphones operate in NSA mode in low bands to benefit fromNSA dual connectivity with high capacity LTE layers. Thus, there is aneed for a network-based mechanism to select and control when aUE-device should be allowed to attach in SA or NSA mode based on certainaspects. This network-based control can vary from market (i.e.,location) to market and/or from device/user to user.

Systems and methods described herein provide for network-based selectionof a UE device's 5G operation mode. According to an implementation, thesystems and methods may overrule a default selection of the highestoperation mode signaled by the UE device and/or configured on the UEdevice when the UE device reports its capabilities. For example, aservice provider may decide that NSA mode will provide a better userexperience than SA mode for a UE device that is capable of both SA andNSA modes.

According to implementations described herein, the network decisions fora UE device's operating mode may take into account policy considerationssuch as (a) geographical location of a UE device, (b) frequency bandsavailable at the UE device's location, (c) traffic load in an area, (d)subscription parameters, such as services supported, quality of service(QoS) requirements, and past service mean opinion score (MOS)measurements. According to another implementation, a policy may takeinto account other factors, such as provisioned attributes, use cases,historical network performance data, and/or network capabilitiesprovisional attributes.

FIG. 1 is a diagram of an exemplary multi-RAT environment 100 in whichthe systems and/or methods, described herein, may be implemented. Asillustrated, environment 100 includes an access network 110 and a corenetwork 150. Access network 110 includes access devices 115, and corenetwork 150 includes core devices 155. Environment 100 further includesUE devices 180-1 through 180-N (collectively referred to herein as UEdevices 180).

The number, the type, and the arrangement of devices in access network110 and core network 150, as illustrated and described, are exemplary. Anetwork device, a network element, or a network function (referred toherein simply as a network device) may be implemented according to oneor multiple network architectures (e.g., a client device, a serverdevice, a peer device, a proxy device, a cloud device, a virtualizedfunction, and/or another type of network architecture (e.g., SoftwareDefined Networking (SDN), virtual, logical, network slicing, etc.)).Additionally, a network device may be implemented according to variouscomputing architectures, such as centralized, distributed, cloud (e.g.,elastic, public, private, etc.), edge, fog, and/or another type ofcomputing architecture.

Environment 100 includes communication links between devices.Environment 100 may be implemented to include wired, optical, and/orwireless communication links among the network devices and the networksillustrated. A communication link may be direct or indirect. Forexample, an indirect communication link may involve an intermediarydevice and/or an intermediary network (not illustrated in FIG. 1). Adirect communication link may not involve an intermediary device and/oran intermediary network. The number and the arrangement of communicationlinks illustrated in environment 100 are exemplary.

Environment 100 may include various planes of communication including,for example, a control plane, a user plane, and a network managementplane. Environment 100 may include other types of planes ofcommunication. A message communicated in support of selecting a 5Goperation mode may use at least one of these planes of communication.Additionally, an interface of a network device may be implementeddifferently from standard interfaces (e.g., an interface defined by astandards body, such as Third Generation Partnership Project (3GPP),International Telecommunication Union (ITU), European TelecommunicationsStandards Institute (ETSI), etc.) in order to support the communication(e.g., transmission and reception of messages, information elements(IE), attribute value pairs (AVPs), etc.) between network devices (e.g.,access devices 115 and/or core devices 155), as described herein.According to various exemplary implementations, the interface may be aservice-based interface or a reference point-based interface.

Access network 110 may include multiple networks of multiple types andtechnologies. For example, access network 110 may include a 4G RAN, a4.5G RAN, a 5G RAN, and/or another type of future generation RAN. By wayof further example, access network 110 may be implemented to include anEvolved UMTS Terrestrial Radio Access Network (E-UTRAN) of a LTEnetwork, an LTE-Advanced (LTE-A) network, and/or an LTE-A Pro network,and a next generation (NG) RAN. Access network 110 may further includeother types of wireless networks, such as a WiFi network, a WorldwideInteroperability for Microwave Access (WiMAX) network, a local areanetwork (LAN), or another type of network (e.g., a legacy ThirdGeneration (3G) RAN, etc.) that may provide an on-ramp to access devices115 and/or core network 150.

According to various exemplary embodiments, access network 110 may beimplemented to include various architectures associated with wirelessservices, such as, for example, macrocell, microcell, femtocell,picocell, metrocell, NR cell, LTE cell, non-cell, or another type ofcell architecture. Additionally, according to various exemplaryembodiments, access network 110 may be implemented according to variouswireless technologies (e.g., RATs, etc.), wireless standards, wirelessfrequencies/bands/carriers, licensed radio spectrum, unlicensed radiospectrum, and/or other attributes of radio communication.

Access network 110 may include different and multiple functionalsplitting, such as options 1, 2, 3, 4, 5, 6, 7, or 8 that relate tocombinations of different types of access network 110 and core network150 including an EPC network and/or a NGC network, or the splitting ofthe various layers (e.g., physical layer, Media Access Control (MAC)layer, Radio Link Control (RLC) layer, and Packet Data ConvergenceControl (PDCP) layer), plane splitting (e.g., user plane, control plane,etc.), centralized unit (CU) and distributed unit (DU), interfacesplitting (e.g., F1-U, F1-C, E1, Xn-C, Xn-U, X2-C, Common Public RadioInterface (CPRI), etc.) as well as other types of network services, suchas dual connectivity (DC) or higher (e.g., a secondary cell group (SCG)split bearer service, a master cell group (MCG) split bearer, an SCGbearer service, NSA, SA, etc.), carrier aggregation (e.g., intra-band,inter-band, contiguous, non-contiguous, etc.), network slicing,coordinated multipoint (CoMP), various duplex schemes (e.g., frequencydivision duplex (FDD), time division duplex (TDD), half-duplex FDD,etc.), and/or another type of connectivity service.

Depending on the implementation, access network 110 may include one ormultiple types of network devices, such as access devices 115. Forexample, access devices 115 may include an eNB, a gNB, an evolved LongTerm Evolution (eLTE) eNB, a radio network controller (RNC), a remoteradio head (RRH), a baseband unit (BBU), a small cell node (e.g., apicocell device, a femtocell device, a microcell device, a home eNB, arepeater, etc.), or another type of wireless node. A “cell” may includea coverage area served by an access device 115 using a particularfrequency band. Thus, in some cases, a cell and the access deviceservicing the cell may be referred to interchangeably. According to anexemplary embodiment, access device 115 includes logic that supports NSAand/or SA operation modes for 5G networks, as described herein.

Core network 150 may include multiple networks of multiple types andtechnologies. According to an exemplary embodiment, core network 150includes a complementary network of access network 110. For example,core network 150 may be implemented to include an EPC of an LTE, a corenetwork of an LTE-Advanced (LTE-A) network, and/or a core network of anLTE-A Pro network, and a next generation core (NGC) network. Corenetwork 150 may also include a legacy core network.

Depending on the implementation, core network 150 may include varioustypes of network devices, such as core devices 155. For example, coredevices 155 may include a packet gateway (PGW), a serving gateway (SGW),a home subscriber server (HSS), an authentication, authorization, andaccounting (AAA) server, a mobility management entity (MME), a policycharging and rules function (PCRF), a charging system (CS), a user planefunction (UPF), an access and mobility management function (AMF), asession management function (SMF), a unified data management (UDM)device, an authentication server function (AUSF), a network sliceselection function (NSSF), a network repository function (NRF), a policycontrol function (PCF), a network exposure function (NEF), and/or anapplication function (AF). According to other exemplary implementations,core devices 155 may include additional, different, and/or fewer networkdevices than those described. For example, core devices 155 may includea non-standard and/or proprietary network device. As another example,core devices 155 may include combined functions, such as overlapping4G/5G functions to support a NSA architecture. According to an exemplaryembodiment, core device 155 includes logic that supports networkselection of a 5G operation mode, as described herein.

UE device 180 includes a device that has computational and wirelesscommunication capabilities. Depending on the implementation, UE device180 may be a mobile device, a portable device, a stationary device, adevice operated by a user, or a device not operated by a user. Forexample, UE device 180 may be implemented as a Mobile Broadband device,a Machine Type Communication (MTC) device, an Internet of Things (IoT)device, an enhanced MTC device (eMTC) (also known as Cat-M1), aNarrowBand IoT (NB-IoT) device, a machine-to-machine (M2M) device, auser device, or other types of wireless end nodes. By way of furtherexample, UE device 180 may be implemented as a smartphone, a personaldigital assistant, a tablet, a netbook, a wearable device (e.g., awatch, glasses, etc.), a set top box, an infotainment system in avehicle, a vehicle support system, a telematics system, a smarttelevision, a game system, or other types of wireless end devices. UEdevice 180 may be configured to execute various types of software (e.g.,applications, programs, etc.). The number and the types of software mayvary among UE devices 180.

UE device 180 may support multiple RATs (e.g., 4G, 5G, future RAT, etc.)and various portions of the radio spectrum (e.g., multiple frequencybands, multiple carrier frequencies, licensed, unlicensed, etc.),network slicing, DC service, and/or other types of connectivityservices. Additionally, UE device 180 may include one or multiplecommunication interfaces that provide one or multiple (e.g.,simultaneous) connections via the same or different RATs, frequencybands, carriers, network slices, and so forth. The multimodecapabilities may vary among UE devices 180. According to an exemplaryembodiment, UE device 180 includes logic that enables networkconnectivity in NSA or SA operation mode, as described herein. Accordingto exemplary embodiments, when UE device 180 supports both NSA or SAoperation modes, access network 110 may apply policies to govern theselection of NSA or SA operation mode for the UE device 180. Thus,similar UE devices 180 may be directed into different operation modes(e.g., NSA or SA) by access network 110 depending, for example onnetwork policy designs.

FIG. 2 is a diagram illustrating exemplary network elements forselection of a 5G operation mode in a portion 200 of multi-RATenvironment 100. As illustrated, network portion 200 includes UE device180, an access network 210, an EPC network 250, and a NGC network 260.Access network 210 includes a combined eNB/gNB 215. EPC network 250includes an MME 252 and a SGW 254; and NGC network 260 includes an AMF262, a UDM 264, a PCF 266, a network data analytics function (NWDAF)268, and a combined UPF with General Packet Radio Service (GPRS)Tunneling Protocol (GTP) device 270. As previously described in relationto environment 100, the number of network devices, the type of networkdevices, the communication links, and so forth, in network portion 200are exemplary.

Combined eNB/gNB 215 may include a network device and other componentsthat allow UE device 180 to wirelessly connect to access EPC network 250and NGC network 260 via access network 210. According to theimplementation of FIG. 2, for NSA operations eNB/gNBs 215 may useportions of the lower frequency bands that are part of (but distinctfrom) the lower frequency bands allocated for LTE communications. Forexample, in one implementation, eNB/gNBs 215 may be configured toallocate portions of a spectrum (e.g., Band 2, 1900 PCS) for 4G and 5Gconnections. In another implementation, eNB/gNBs 215 may support SAoperations using mmWave frequencies. In one implementation, eNB/gNBs 215may interface with EPC network 250 via a Diameter S1 interface andinterface with NGC network 260 via an N3 interface. Functions of MME252, SGW 254; AMF 262, UDM 264, PCF 266, NWDAF 268, and UPF+GTP device270 are described further in connection with, for example, FIGS. 3A-3D.

FIGS. 3A-3D are diagrams illustrating exemplary communications inportion 300 of network environment 100 for performing network selectionof a 5G operation mode. As illustrated, network portion 300 includes UEdevice 180, access network 210, EPC network 250, and NGC network 260.Access network 210 includes a combined eNB/gNB 215, EPC network 250includes MME 252, and NGC network 260 includes AMF 262, UDM 264, PCF266, and NWDAF 268.

Referring to FIG. 3A, according to an exemplary scenario, assume that UEdevice 180 establishes a radio resource control (RRC) connection witheNB/gNBs 215 based on an RRC Connection Establishment procedure 305.Subsequently, UE device 180 and NGC network 260 may perform an accessregistration procedure 310.

Referring to FIG. 3B, according to one implementation, during accessregistration procedure 310, AMF 262 may provide to PCF 266 a policyquery 315 pertaining to UE device 180. A binding service function (BSF,not shown) may assist AMF 262 in establishing communication with PCF266. Policy query 315 may request access management policies for UEdevice 180 or, more specifically, policy query 315 may request a 5Goperation mode policy for UE device 180. Policy query 315 may request,for example, information about operation mode capabilities of UE device(e.g., NSA and/or SA). According to an implementation, policy query 315may be included in existing call flows configured for AMF and PCFinteraction.

Based on policy query 315, PCF 266 may apply a 5G operation modeselection model to determine whether or not to override UE devicecapability information (e.g., SA and NSA 5G operation modes) whennetwork conditions would otherwise permit SA operation mode. In oneimplementation, PCF 266 may dynamically apply the 5G operation modeselection model by collecting stored subscription data for UE device180, stored network data relevant to UE device 180, and/or dynamicnetwork data relevant to UE device 180. The stored subscription data andthe stored network data may be maintained, for example, in a localmemory of PCF 266. As indicated at reference 317, PCF 266 may obtain thecurrent network data via a subscription with NWDAF 268.

As indicated at reference 320, PCF 266 may apply the stored subscriptiondata, the stored network data, and/or the dynamic network data to the 5Goperation mode selection model to dynamically assign a RAT/FrequencySelection and Prioritization (RFSP) value for UE device 180. The RFSPvalue may include an index value indicating a preferred 5G mode for UEdevice 180. For example, the index value may indicate that UE device 180is SA capable, and another index value may indicate that UE device 180is NSA capable. Policy considerations applied by PCF 266 to determinethe RFSP value are described further, for example, in connection withFIGS. 4B and 4C. PCF 266 may provide the determined RFSP value 325 toAMF 262 for propagation and implementation.

FIG. 3C provides an alternate set of communications to those of FIG. 3B.Referring to FIG. 3C, according to another implementation, during accessregistration procedure 310, AMF 262 may obtain, from UDM 264,subscription information 327 pertaining to UE device 180. Subscriptioninformation 327 may include a specific RFSP value corresponding to asubscription for UE device 180. For example, an RFSP value stored by UDM264 may be preselected to correspond to a subscription category (e.g.,IoT vs. consumer) or service type (e.g., Wireless Priority Service(WPS), E911, etc.) associated with UE device 180.

Referring to FIG. 3D, AMF 262 may receive the selected RFSP value fromPCF 266 (e.g., RFSP value 325 of FIG. 3B) or the pre-designated RFSPvalue from UDM 264 (e.g., RFSP value 327 of FIG. 3C), depending on theimplementation used in NGC network 260. AMF 262 may forward 330 thereceived RFSP value to eNB/gNBs 215. eNB/gNBs 215 and UE device 180 mayapply corresponding policies based on the RFSP value. For example, RFSPinformation may be used to select a different AMF 262 if necessary,manage idle mode camping, and controlling of inter-RAT/inter-frequencyhandover while inactive mode.

FIGS. 3A-3D illustrate an exemplary process of network-based selectionof a UE device's 5G operation mode. However, according to otherexemplary embodiments, the process may include additional, different,and/or fewer steps, and/or include additional, different, and/or fewermessages.

FIGS. 4A-4C are diagrams illustrating an exemplary embodiment of a 5Goperation mode selection model 400 that may be applied, for example, byPCF 266. As shown in FIG. 4A, along with 5G operation mode selectionmodel 400, PCF 266 may also store subscriber profiles 402. Subscriberprofiles 402 may include subscriber data, subscription data,preferences, and policies associated with different UE devices 180. Inaddition to communications described above in connection with FIG. 3B,PCF 266 may also retrieve UE device profile data 404 in response toreceiving policy query 315. Thus, PCF 260 may apply dynamic network data317 (e.g., from NWDAF 268) and UE device profile data 404 to 5Goperation mode selection model 400 to assign and provide RFSP value 325.

As shown in FIGS. 4B and 4C, selection model 400 may be in the form of atable that includes UE capability 405 field, a subscription type field410, a device type field 415, a service type field 420, a PCF RFSP field425, a UE geographic location field 430, an available frequency field435, a load field 440, a time of day field 445, a subscription (service)field 450, a subscription (QoS) field 455, a mean opinion score (MOS)field 460, and a network slice selection assistance information (NSSAI)field 465. Each of fields 405-465 may represent design parameters thatcan be weighted or applied to determine a network assigned RFSP valuefor a particular UE. The 5G operation mode selection model 400 ispresented in the form of a table in FIGS. 4B and 4C for illustrationpurposes. In other implementations, a different data format may be usedfor model 400.

Referring to FIG. 4B, UE capability field 405 may include operation modecapabilities information for a UE device 180. Generally, for purposes of5G operation mode selection, UE capabilities may include both SA andNSA. Subscription type field 410 may include a subscription typeinformation associated with UE device 180. The subscription types mayinclude, for example, consumer and IoT, where consumer subscriptions mayweigh toward using an available SA band, while IoT subscriptions mayweigh toward using an NSA band.

Device type field 415 may include information indicating a type of UEdevice 180, such as a smartphone, a fixed wireless device, a telematicsdevice, an IoT device, etc. Service type field 420 may includeinformation indicating a service type designated by a subscription oruse case. Service type filed 420 may distinguish, for example, betweenWPS, emergency service, conventional data sessions, etc.

PCF RFSP field 425 may include a default RFSP value for UE device 180.The default RFSP value may signal to the RAN which radio managementstrategies/polices should be used for a particular UE (e.g., schedulingpriority, preference of certain bands over another, etc.). UE geographiclocation field 430 may include a current geographic location (e.g., inreal time) of UE device 180. Geographic location information mayinclude, for example, a tracking area ID (TAI), an E-UTRAN cell globalidentifier (ECGI), or another location parameter.

Available frequency field 435 may include a list of available frequencybands for the current location specified in UE geographic location field430. Bands in available frequency field 435 may include, for example,bands (or combinations of bands) to support NSA and/or SA operationmodes. According to an implementation, available frequency bands may bepre-provisioned information that can be determined, for example, basedon cross-reference to a current TAI or ECGI.

Load field 440 may include a traffic load rating for bands specified infrequency field 435 (e.g., and associated with an area identifier fromUE geographic location field 430). Values in load field 440 may beexpressed as a capacity percentage, a threshold indication (e.g., low,medium, high), or an available bandwidth value. In one implementation,values in load field 440 may be supplied to PCF 266, for example, byNWDAF 268 and updated in real time. In another implementation, values inload field 440 may include load projections obtained, for example, froma network data module (e.g., NWDAF 268).

Time of day field 445 may include time window information andcorresponding load projections for cells associated with UE device 180.For example, a time of day of an RRC connection may be correlated toprojection period with a low, medium, or high traffic load.

Subscription (service) field 450 may include a list of services orservice parameters to be supported for a subscription associated with UEdevice 180. Services may include, for example, data only, voice anddata, etc. Subscription (QoS) field 455 may include a quality of serviceinformation associated with a subscription. Parameters for subscription(service) field 450 and subscription (QoS) field 455 may be available toPCF 266, for example, from stored subscriber policies.

Referring to FIG. 4C, MOS field 460 may include past service MOSmeasurements. The MOS measurements may correspond to a particular timeof day, geographic area, and/or frequency bands associated with UEdevice 180. According to another implementation, MOS field 460 mayinclude an expected/predicted MOS value. In one implementation, valuesin MOS field 460 may be supplied to PCF 266, for example, from a networkdata module (e.g., NWDAF 268).

NSSAI field 465 may include an indication of whether network sliceselection assistance information has been requested by UE device 180.The NSSAI may indicate the services and/or characteristics required byan application being executed on UE device 180. A UE device's requestfor network slicing, for example, may weigh in favor of using SAoperation mode, if network slicing is available in NSA mode.

As described above, PCF 266, for example, may apply values in fields405-465 to determine a resulting network-selected RFSP value for UEdevice 180. According to an implementation, PCF 266 may match values fora current UE 180 to fields 405-465 to determine a corresponding value inan operator-defined RFSP field 470. In one implementation, PCF 266 mayidentify a best fit of fields 405-465 to determine a value for RFSPfield 470. In another implementation, one or more of fields 405-465 maybe weighted to trump other RFSP selection criteria.

In still other implementations, a combination of provisional attributes(e.g., subscription type), historical network performance data (e.g.,NSA to SA jitter), network capabilities (e.g., number of frequency bandswith Dynamic Spectrum Sharing (DSS) enabled in a given geographicalfootprint, typical carrier aggregation capability across deployed bandsin NSA vs SA modes, number and density of gNBs SA-enabled in a givengeographical footprint, etc.).

Selection of a value from operator-defined RFSP field 470 may directparticular policy actions by RAN 210, AMF 262, and/or MME 252. Forexample, as shown in fields 475 and 480, values in operator-defined RFSPfield 470 may correspond to a particular band (e.g., low, medium, high)and operation mode (e.g., NSA or SA) for UE device 180. Application of aselected value from operator-defined RFSP field 470 may also directactions by AMF 262 and MME 252, as indicated in AMF action field 485 andMME action field 490, respectively.

Although model 400 shows 13 design freedoms that may be applied todetermine an operator-defined RFSP value, in other implementations,model 400 may include additional or fewer design parameters than thoseillustrated. Furthermore, PCF 266, for example, may apply one of severalselection techniques to determine the operator-defined RFSP value fromthe design freedoms in model 400. For example, machine learning and/orartificial intelligence may be used to perform an RFSP selection ordetermine weight values for one or more of fields 405-465. In anotherimplementation, model 400 may not include dynamic network data. Forexample, model 400 may be applied by UDM 264 to match UE device typeinformation to a designated RFSP value in field 470. Furthermore, fields475-490 are shown for descriptive purposes and may not be used by PCF266 to select an RFSP value.

FIG. 5 is a diagram illustrating exemplary components of a device 500that may be included in one or more of the devices described herein. Forexample, device 500 may correspond to components included in accessdevices 115, core devices 155, UE device 180, eNB/gNB 215, MME 252, SGW254, AMF 262, UDM 264, PCF 266, and UPF+GTP 268. As illustrated in FIG.5, device 500 includes a bus 505, a processor 510, a memory/storage 515that stores software 520, a communication interface 525, an input 530,and an output 535. According to other embodiments, device 500 mayinclude fewer components, additional components, different components,and/or a different arrangement of components than those illustrated inFIG. 5 and described herein.

Bus 505 includes a path that permits communication among the componentsof device 500. For example, bus 505 may include a system bus, an addressbus, a data bus, and/or a control bus. Bus 505 may also include busdrivers, bus arbiters, bus interfaces, clocks, and so forth.

Processor 510 includes one or multiple processors, microprocessors, dataprocessors, co-processors, application specific integrated circuits(ASICs), controllers, programmable logic devices, chipsets,field-programmable gate arrays (FPGAs), application specificinstruction-set processors (ASIPs), system-on-chips (SoCs), centralprocessing units (CPUs) (e.g., one or multiple cores), microcontrollers,and/or some other type of component that interprets and/or executesinstructions and/or data. Processor 510 may be implemented as hardware(e.g., a microprocessor, etc.), a combination of hardware and software(e.g., a SoC, an ASIC, etc.), may include one or multiple memories(e.g., cache, etc.), etc.

Processor 510 may control the overall operation or a portion ofoperation(s) performed by device 500. Processor 510 may perform one ormultiple operations based on an operating system and/or variousapplications or computer programs (e.g., software 520). Processor 510may access instructions from memory/storage 515, from other componentsof device 500, and/or from a source external to device 500 (e.g., anetwork, another device, etc.). Processor 510 may perform an operationand/or a process based on various techniques including, for example,multithreading, parallel processing, pipelining, interleaving, etc.

Memory/storage 515 includes one or multiple memories and/or one ormultiple other types of storage mediums. For example, memory/storage 515may include one or multiple types of memories, such as, a random accessmemory (RAM), a dynamic random access memory (DRAM), a static randomaccess memory (SRAM), a cache, a read only memory (ROM), a programmableread only memory (PROM), an erasable PROM (EPROM), an electrically EPROM(EEPROM), a single in-line memory module (SIMM), a dual in-line memorymodule (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solidstate memory, and/or some other type of memory. Memory/storage 515 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a Micro-ElectromechanicalSystem (MEMS)-based storage medium, and/or a nanotechnology-basedstorage medium. Memory/storage 515 may include drives for reading fromand writing to the storage medium.

Memory/storage 515 may be external to and/or removable from device 500,such as, for example, a Universal Serial Bus (USB) memory stick, adongle, a hard disk, mass storage, off-line storage, or some other typeof storing medium (e.g., a compact disk (CD), a digital versatile disk(DVD), a Blu-Ray disk (BD), etc.). Memory/storage 515 may store data,software, and/or instructions related to the operation of device 500.

Software 520 includes an application or a program that provides afunction and/or a process. As an example, with respect to access device115 (e.g., eNB/gNB 215, etc.), software 520 may include an applicationthat, when executed by processor 510, provides a function to enforcenetwork-based selection of a UE device's 5G operation mode, as describedherein. Additionally, with reference to a network device of a corenetwork (e.g., UDM 264, PCF 266, etc.), software 520 may include anapplication that, when executed by processor 510, provides a function toselect a UE device's 5G operation mode, as described herein. Software520 may also include firmware, middleware, microcode, hardwaredescription language (HDL), and/or other form of instruction. Software520 may also be virtualized. Software 520 may further include anoperating system (OS) (e.g., Windows, Linux, Android, proprietary,etc.).

Communication interface 525 permits device 500 to communicate with otherdevices, networks, systems, and/or the like. Communication interface 525includes one or multiple wireless interfaces and/or wired interfaces.For example, communication interface 525 may include one or multipletransmitters and receivers, or transceivers. Communication interface 525may operate according to a protocol stack and a communication standard.Communication interface 525 may include an antenna. Communicationinterface 525 may include various processing logic or circuitry (e.g.,multiplexing/de-multiplexing, filtering, amplifying, converting, errorcorrection, application programming interface (API), etc.).Communication interface 525 may be implemented as a point-to-pointinterface, a service based interface, etc.

Input 530 permits an input into device 500. For example, input 530 mayinclude a keyboard, a mouse, a display, a touchscreen, a touchlessscreen, a button, a switch, an input port, speech recognition logic,and/or some other type of visual, auditory, tactile, etc., inputcomponent. Output 535 permits an output from device 500. For example,output 535 may include a speaker, a display, a touchscreen, a touchlessscreen, a light, an output port, and/or some other type of visual,auditory, tactile, etc., output component.

As previously described, a network device may be implemented accordingto various computing architectures (e.g., in a cloud, etc.) andaccording to various network architectures (e.g., a virtualizedfunction, etc.). Device 500 may be implemented in the same manner. Forexample, device 500 may be instantiated, spun up, spun down, or undergoa life-cycle, using well-known virtualization techniques in apublic/private cloud or other type of network.

Device 500 may perform a process and/or a function, as described herein,in response to processor 510 executing software 520 stored bymemory/storage 515. By way of example, instructions may be read intomemory/storage 515 from another memory/storage 515 (not shown) or readfrom another device (not shown) via communication interface 525. Theinstructions stored by memory/storage 515 cause processor 510 to performa process described herein. Alternatively, for example, according toother implementations, device 500 performs a process described hereinbased on the execution of hardware (processor 510, etc.).

FIG. 6 is an illustration of a use case for network-based selection of aUE device's 5G operation mode in a portion 600 of network environment100. Network portion 600 may include a 5G cell 605 that supports both SAand NSA modes, a 5G NSA cell 610, and a 5G NSA cell 615. Cell 605 islocated within cell 610. End devices 180-1, 108-2, and 180-3 aredual-mode UEs, capable of operating in either SA or NSA mode. In theexample, of FIG. 6, assume UE device 180-1 is a fixed wireless device(e.g., a wireless hot spot), UE device 180-2 is an IoT device, and 180-3is a consumer's smart phone.

In the example of FIG. 6, both UE device 180-1 and 180-2 may be locatedwithin the coverage area of cell 605 and report dual capabilities. Basedon RFSP values selected by PCF 266 (not shown), AMF 262 may direct UEdevice 180-1 to use an SA frequency band (e.g., mmWave frequency) forcell 605. Accordingly, UE device 180-1 may communicate with NGC core 260via 5G standalone infrastructure. Conversely, again based on RFSP valuesselected by PCF 266, AMF 262 may direct UE device 180-2 to use an NSAfrequency band for cell 610. Accordingly, UE device 180-2 maycommunicate with NGC core 260 via 5G non-standalone infrastructure eventhough UE device 180-2 may be otherwise configured to use 5G standaloneresources. UE device 180-3, which is located in a cell 615 that onlysupports NSA operation mode, would not be subject to network overrulingof a 5G operation mode, since only NSA is available in cell 615.

FIG. 7 is a flow diagram of a process 700 for performing network-basedselection of a UE device's 5G operation mode. According to an exemplaryembodiment, a network device of a NGC network performs steps of process700. For example, the network device may be PCF. According to anotherembodiment, a PCF, AMF, and/or access device (e.g., gNB/eNB 215) mayperforms steps of process 700. Additionally, for example, processor 510may execute software 520 to perform a step illustrated in FIG. 7 anddescribed herein. Additionally, or alternatively, a step illustrated inFIG. 7 may be performed by only hardware.

Process 700 may include storing a 5G mode selection model (block 705),receiving an access query for a UE device (block 710), and determiningif the UE device is SA and NSA capable (block 715). For example, PCF 266may be configured with 5G operation mode selection model 400. As part ofan initial attachment procedure or another network communicationprocess, AMF 262 may provide to PCF 266 a policy query pertaining to UEdevice 180. PCF 266 may use a UE identifier in the policy query anddevice capability information (e.g., from the policy query or from astored subscriber profile) to determine if UE device 180 has both SA andNSA capability.

If the UE device is both SA and NSA capable (block 715—Yes), process 700may include identifying UE device data for the 5G selection model (block720) and assigning an RFSP value for the UE device based on the model(block 725). For example, PCF 266 may retrieve data from subscriberprofiles 402 and NWDAF 268 to use in 5G operation mode selection model400. Based on the model output, PCF 266 may select a RFSP value (e.g.,from operator-defined RFSP field 470).

Process 700 may also include sending the assigned RFSP value to an AMF(block 730), and applying the assigned RFSP value to overrule UEdevice-reported capabilities and/or trigger an inter-RAT handover (block735). For example, PCF 266 may provide the determined RFSP value to AMF262 for propagation and implementation. AMF 262 may receive the selectedRFSP value and forward the received RFSP value to a correspondingeNB/gNB 215. According to one implementation, the RFSP value may triggeran inter-RAT handover process for UE device 180. For example, a UEdevice 180 that is capable of both SA and NSA mode may be currentlyattached to network in SA mode (e.g., due to UE device default selectionor other initial attachment data). In that case, UE device 180 may beforced to be moved to an appropriate NSA mode through an inter-RAThandover process based on the RFSP value communicated to AMF 262 andeNB/gNB 215.

If the UE device is not both SA and NSA capable (block 715—No), process700 may include applying an operation mode based on the UE devicereported capabilities (block 740). For example, PCF 266 will notevaluate whether to overrule a UE device's operation mode when only bothSA and NSA mode capabilities are not available to UE device 180.

Systems and methods provide for network-based selection of a UE device's5G operation mode. A network device in a wireless core network receivesan access request for a UE device. The UE device is capable of 5G NSAand 5G SA operation modes. The network device identifies one or more ofsubscription data for the UE device, stored network data associated withthe UE device, or dynamic network data relevant to the UE device andassigns, based on the identifying, a RFSP value for the UE device. Thenetwork device sends the RFSP value to an access management function inthe wireless core network for controlling selection of the 5G NSAoperation mode or 5G SA operation mode.

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. Various modifications and changes may be madethereto, and additional embodiments may be implemented, withoutdeparting from the broader scope of the invention as set forth in theclaims that follow. The description and drawings are accordingly to beregarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while series of signals and blocks have been described withregard to the processes illustrated in FIGS. 3A-3D, and 7, the order ofthe signals and blocks may be modified according to other embodiments.Further, non-dependent signals or blocks may be performed in parallel.Additionally, other processes described in this description may bemodified and/or non-dependent operations may be performed in parallel.

Embodiments described herein may be implemented in many different formsof software executed by hardware. For example, a process or a functionmay be implemented as “logic,” a “component,” or an “element.” Thelogic, the component, or the element, may include, for example, hardware(e.g., processor 510, etc.), or a combination of hardware and software.

Embodiments have been described without reference to the specificsoftware code because the software code can be designed to implement theembodiments based on the description herein and commercially availablesoftware design environments and/or languages. For example, varioustypes of programming languages including, for example, a compiledlanguage, an interpreted language, a declarative language, or aprocedural language may be implemented.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

Additionally, embodiments described herein may be implemented as anon-transitory computer-readable storage medium that stores data and/orinformation, such as instructions, program code, a data structure, aprogram module, an application, a script, or other known or conventionalform suitable for use in a computing environment. The program code,instructions, application, etc., is readable and executable by aprocessor (e.g., processor 510) of a device. A non-transitory storagemedium includes one or more of the storage mediums described in relationto memory 515.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, it should be understood that suchinformation shall be collected, stored and used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage and use of such information may besubject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as may be appropriatefor the situation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, act, or instruction set forth in this description should beconstrued as critical or essential to the embodiments described hereinunless explicitly indicated as such. All structural and functionalequivalents to the elements of the various aspects set forth in thisdisclosure that are known or later come to be known are expresslyincorporated herein by reference and are intended to be encompassed bythe claims.

What is claimed is:
 1. A method, comprising: receiving, by one or morenetwork devices in a wireless core network, a policy query for a userequipment (UE) device, wherein the UE device is capable of 5Gnon-standalone (NSA) and 5G standalone (SA) operation modes;identifying, by the one or more network devices, one or more ofsubscription data for the UE device, stored network data associated withthe UE device, or dynamic network data relevant to the UE device;assigning, by the one or more network devices and based on theidentifying, a radio access technology/frequency selection andprioritization (RFSP) value for the UE device; and sending, by the oneor more network devices, the RFSP value to an access management functionin the wireless core network for controlling selection of the 5G NSAoperation mode or 5G SA operation mode.
 2. The method of claim 1,wherein identifying the subscription data includes retrievinginformation from a stored subscriber profile for the UE device.
 3. Themethod of claim 1, wherein identifying the dynamic network dataincludes: identifying a current traffic load for different frequencybands available to the UE device; or identifying a projected trafficload for different frequency bands available to the UE device.
 4. Themethod of claim 1, wherein identifying the stored network data includes:identifying a type of service for an application on the UE device, oridentifying a quality of service requirement for an application on theUE device.
 5. The method of claim 1, wherein identifying the storednetwork data includes: identifying a mean opinion score (MOS) thatcorresponds to a particular time of day, a geographic area, and afrequency band accessible by the UE device.
 6. The method of claim 1,wherein identifying the stored network data incudes: identifying networkslice selection assistance information (NSSAI) associated with the UEdevice.
 7. The method of claim 1, wherein identifying the subscriptiondata incudes: identifying, from a subscriber profile, the UE device asmachine-type communication (MTC) device, or identifying, from thesubscriber profile, a wireless priority service (WPS) indicator or anemergency service indicator.
 8. The method of claim 1, furthercomprising: triggering, by the one or more network devices and inresponse to the sending, an inter-radio access technology (RAT) handoverof the UE device.
 9. The method of claim 1, further comprising: storing,by the one or more network devices, a 5G operation mode selection model,wherein assigning the RFSP value comprises applying the 5G operationmode selection model to the one or more of subscription data for the UEdevice, stored network data associated with the UE device, or dynamicnetwork data relevant to the UE device.
 10. One or more network devices,comprising: one or more processors configured to: receive, from a devicein a wireless core network via the communications interface, policyquery for a user equipment (UE) device, wherein the UE device is capableof 5G non-standalone (NSA) and 5G standalone (SA) operation modes;identify one or more of subscription data for the UE device, storednetwork data associated with the UE device, or dynamic network datarelevant to the UE device; assign, based on the identifying, a radioaccess technology/frequency selection and prioritization (RFSP) valuefor the UE device; and send, in response to the policy query, the RFSPvalue to an access management function in the wireless core network forcontrolling selection of the 5G NSA operation mode or 5G SA operationmode.
 11. The one or more network devices of claim 10, wherein, whenassigning the RFSP value, the one or more processors are furtherconfigured to: apply, to a 5G operation mode selection model, one ormore of the subscription data for the UE device, the stored network dataassociated with the UE device, or the dynamic network data relevant tothe UE device.
 12. The one or more network devices of claim 10, whereinthe one or more network devices include at least one of: a policycontrol function (PCF) for a next generation core network or a unifieddata management (UDM) device for the next generation core network. 13.The one or more network devices of claim 10, wherein, when identifyingthe dynamic network data, the one or more processors are furtherconfigured to: identify a projected traffic load for different frequencybands available to the UE device.
 14. The one or more network devices ofclaim 10, wherein, when identifying the subscription data, the one ormore processors are further configured to: identify a quality of servicerequirement for an application on the UE device.
 15. The one or morenetwork devices of claim 10, wherein, when identifying the storednetwork data, the one or more processors are further configured to:identify a mean opinion score (MOS) that corresponds to a particulartime of day, a geographic area, and a frequency band accessible by theUE device.
 16. The one or more network devices of claim 10, wherein,when identifying the subscription data incudes, the one or moreprocessors further configured to: identify, from a subscriber profile, awireless priority service (WPS) indicator or an emergency serviceindicator.
 17. The one or more network devices of claim 10, wherein theone or more processors are further configured to: determine that the UEdevice is capable of both the NSA operation mode and the SA operationmode.
 18. A non-transitory computer-readable medium containinginstructions executable by at least one processor, the computer-readablemedium comprising one or more instructions for: receiving, by one ormore network devices in a wireless core network, a policy query for auser equipment (UE) device, wherein the UE device is capable of 5Gnon-standalone (NSA) and 5G standalone (SA) operation modes;identifying, by the one or more network devices, one or more ofsubscription data for the UE device, stored network data associated withthe UE device, or dynamic network data relevant to the UE device;assigning, by the one or more network devices and based on theidentifying, a radio access technology/frequency selection andprioritization (RFSP) value for the UE device; and sending, by the oneor more network devices, the RFSP value to an access management functionin the wireless core network for controlling selection of the 5G NSAoperation mode or 5G SA operation mode.
 19. The non-transitorycomputer-readable medium of claim 18, further comprising one or moreinstructions for: storing, by the one or more network devices, a 5Goperation mode selection model for assigning the RFSP value; andapplying, to the 5G operation mode selection model, one or more of thesubscription data for the UE device, the stored network data associatedwith the UE device, or the dynamic network data relevant to the UEdevice.
 20. The non-transitory computer-readable medium of claim 18,further comprising one or more instructions for: determining that the UEdevice is capable of both the NSA operation mode and the SA operationmode.